Payments and Packages

The following diagram illustrates how packages are applied to subscriptions:

Packages and Payments

The following table interprets the diagram:
Tariff > Package > Attribute Explanation
Prepaid > Base

A prepaid subscription can have a base package.

The package must be Recurring and Prepaid.

The package is acquired during subscription creation.

This is charged every month by the Recurring Prepayment batch job, which:

  • Creates a debit (pre-pay) transaction.
  • The transaction, when due, causes a payment to be taken by the Recurring Payment job.

The payment can be charged against a card or prepaid balance.
Prepaid > Bolt-on > Recurring

A prepaid subscription can have recurring bolt-on packages; they do not have to run concurrently,

The package must be configured as Recurring and Prepaid.

The package is acquired via REST web services/AgentView purchase.

This is charged by the Recurring Prepayment batch job, which:

  • Creates a debit (pre-pay) transaction.
  • The transaction, when due, causes a payment to be taken by the Recurring Payment job. The payment can be against a registered card or prepaid balance.

Payment is taken when the bolt-on is due for renewal.
Prepaid > Bolt-on > Non-recurring

A prepaid subscription can have non-recurring bolt-on packages.

The package must be configured as Non-recurring (the same non-recurring bolt-ons can be used for prepaid and postpaid subscriptions).

The package is acquired via REST web services/AgentView purchase.

Paid for up front.
Prepaid > Top-up

A top-up applies to prepaid subscriptions only

The package is acquired via REST web services/AgentView purchase.

Paid for up front with immediate posting of debit (prepaid) transaction and credit (payment).
Postpaid > Base

A postpaid subscription can have a base package.

The package must be configured as Recurring and Postpaid.

The package is acquired during subscription creation.

The package is billed monthly by the Invoice Production batch job.
Postpaid > Bolt-on > Recurring

A postpaid subscription can have recurring bolt-on packages.

The package must be configured as Recurring and Postpaid.

The package is acquired via REST web services/AgentView purchase.

The package is billed monthly by the Invoice Production batch job aligned to the billing cycle date.
Postpaid > Bolt-on > Non-recurring > Purchase PREPAID

A post-paid subscription can have non-recurring bolt-on packages (pre-paid).

The package must be configured as Non-Recurring (the same non-recurring bolt-ons can be used for pre and post paid subscriptions).

This package is acquired via REST web service/AgentView purchase.

Paid for up-front with immediate posting of debit (prepaid) transaction and credit (payment).
Postpaid > Top-up Top-up is not applicable for a postpaid subscription.